2026.1 release notes

January 2026

This 2026.1 release adds a VM-based appliance deployment option to simplify administrative management, introduces a new System Information API endpoint for viewing deployment information, adds PAT support for Snowflake connector, and extends file connector functionality with additional support for AWS S3 and S3-compatible backend. This release also introduces a new consolidated release notes format where new features, fixed issues, and known issues are presented on a single page for easier navigation.

 

On this page:

New features

New VM Appliance deployment method (MSSQL)

Hyperscale now supports a VM-based appliance deployment option in addition to the existing Kubernetes model for new deployments of Hyperscale Compliance.

The VM appliance model follows the structure of the traditional engine based hosting model and provides a more straightforward management experience for administrative teams.

Administrators can perform core system management tasks through the appliance interface, including:

  • Storage management

  • Network management

  • Network security (KeyStore and TrustStore management)

  • Support bundle generation

VM-based deployment is available to Oracle and MSSQL connectors.

 

System Information API: new endpoint

This release introduces a new API GET endpoint /system-information which provides current Hyperscale deployment information.

The /system-information endpoint returns the following:

  • Hyperscale version

  • Deployment dates

  • Deployment and upgrade history

  • Registered masking engine versions

  • Deployed connector type

Currently, the System Information API can only return connector type information for MSSQL and Oracle connectors.

 

File Connector enhancements

  • Added support for AWS S3 staging area
    The Hyperscale file connector now supports AWS S3 as a staging area, providing cloud-native, scalable, and durable storage for file-processing workflows.
    To enable this feature, refer to Configuring AWS S3 bucket as staging area.

  • Added support for S3-compatible backend as source and target
    The Hyperscale file connector now supports S3-compatible backend as source and target. Authentication is currently supported using access key ID and secret access key.

 

Snowflake Connector

The Hyperscale Snowflake connector now supports PAT (Programmatic Access Token) authentication alongside the existing key‑pair–based authentication mechanism.

Fixed issues

Issue number Summary
DLPXECO-13099

The following file connector issues are now fixed:

  • Sometimes Parquet files copied from an S3 source on AWS were corrupted during the unload process. This issue is resolved following multiple enhancements to the unload process.

  • Some users encountered errors when using the file connector to load to AWS S3 with IAM role authentication. This issue is resolved following multiple enhancements to the load process.
DLPXECO-13156 The Hyperscale Snowflake APIs now validate all required database details when a masking job is created. Previously, if incorrect information was provided, the job would fail after job execution. With this fix, the system validates inputs upfront and immediately returns an error if any details are invalid.
DLPXECO-13200 Snowflake Connector: Fixed an issue during load service where concurrent jobs could fail or slow due to Snowflake connection errors, race conditions, and database concurrency handling.
DLPXECO-13266 Resolved an issue where the Mongo unload process generated format files containing entries from previous runs. This fix ensures the format file only includes entries from the current unload operation.
HM-1394

Fixed an issue where jobs could fail if a required mount point became disconnected or unreachable during execution.
HM-4961

Closed Appliance Hyperscale: Fixed an issue that caused Closed Appliance Hyperscale registration in the DCT Engine to fail.
HM-5032 Fixed an issue that caused the Sysadmin CLI to display incorrect values for packagedAppVersions in the list of available upgrade packages.
HM-5219 Kubernetes deployment: Fixed an issue that caused an InvalidImageName error for the database-service image during Kubernetes deployment.
HM-5340 Fixed an issue where differences in microservice databases caused dataset creation to fail during sync import.

Known issues

Issue number

Summary

Workaround

DLPXECO-9149

DLPXECO-12929

In this release, we have identified a limitation in the File Connector related to Parquet file compatibility.

The connector does not currently support the following Parquet data type:

  • INT64 (TIME(MICROS,false))

  • INT64 (TIMESTAMP(NANOS,false))

 

When Parquet files include columns defined with this specific logical type, file ingestion or processing may fail or result in unexpected behaviour.

Use split count as 1 while creating the data_set
HM-5101 Dataset creation does not currently support payloads or file uploads containing more than 10,000 items. Any attempt to upload files exceeding this limit will fail.

None

HM-3636

MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response.

None
HM-1397 Oracle Load fails for table having triggers only with SQL*Loader-937 error. None

EOL (end-of-life) notice

Docker Compose - May 2026

Docker Compose deployments for Hyperscale Compliance will reach End of Life (EOL) in May 2026. For more information, refer to Deprecated and EOL notices.